Disable timer mocking and enable verbose output.

* Creating a new app in the current directory

* Fixed style mistakes

Fixes react#391

* Add Surge.sh to deploy instructions

* Add it also to the Table of Contents

Thanks to @geowarin for the tip in react#401 (comment)

Ref react#387

* Load favicon through html-loader.

Fixes react#291.

* Add test for *.ico in e2e test suite

* Configure html-loader to process <link href="...">

* Address feedback on html-loader inclusion.

* Place favicon.ico at the root of the build dir

* Make comment style consistent between prod and dev webpack configs

* Fix html-loader config in dev mode

This will work correctly when there are duplicate filenames in different paths.
Fixes: react#445

* add off font format to loaders

* add otf format support

This rule is considered dangerous in certain situations. This is especially true for Immutable.js users. See the discussion at issue react#465 for more information about this.

Small typo line 572 "becasue" to "because"

According to the official SemVer FAQ, versioning should start at 0.1.0 (http://semver.org/#how-should-i-deal-with-revisions-in-the-0yz-initial-development-phase)

* Get latest version numbers of react and react-dom from npm before install.

* Run separate npm installs for react, react-dom, and react-test-renderer.

* Consolidate into a single npm install.

* Fix misplaced parenthesis, add missing semicolon.

* Add missing semicolon.

* Started using babel-preset-latest

* Updated babel dependencies

* Remove redundant babel-plugin-syntax-async-functions

* Disabled redundant regenerator transform

* Clean up e2e script

* Link to local packages after ejecting

* Exit on any errors passed in build stats

* Match console error output in start.js

react#878)

* Disable ES2015 transforms based on node version using babel-preset-env

* pass major version number for node to babel-preset-env instead of version string

* use parseFloat() instead of parseInt() to parse node version

* fixed style nits

* Update react-scripts dependencies to use jest 16

* Remove testRegex from Jest config (now default)

)

* Support passing scoped package names to --scripts-version arg

* Factor out bitwise operator in indexOf test

* Comment on stripping only version or tag from package name arg

)

* Dispose error overlay when linting errors have been corrected

* Fixed spelling error

* Minor style tweaks

* Create asset filenames mapping on the build output

I use danethurber/webpack-manifest-plugin on Webpack production
configuration to create a file named `asset-manifest.json` which contain a
mapping of all asset filenames to their corresponding output file.

`asset-manifest.json` will be located at the root of output folder.

This'll resolve react#600

* Add an explanation for ManifestPlugin

* Make webpack-manifest-plugin's version exact

…eact#876)

* Add supports for prelease tags version

* Add comment to regex

* Cut everything after the first -\d

* Make semver version optional, so just package name get parsed correctly

Running tests with the `-u` flag is a more reliable way to upgrade,
because the watch mode only runs tests for changed files.

* Added note about env server restart

As discussed in [react#870](react#870)

* Style nit

…#927)

* Enable babel parameters/destructuring for all versions of Node

* Add more descriptive comment explaining plugin use

* Update dependencies

* Use published version of eslint-config-react-app for development

We dogfood on our eslint-config-react-app by using it as our ESLint config,
but installing it from the local folder causes problems when its peerDependencies
are updated, because npm won't update it unless the version number changes.

Use the published version for dogfooding so it can be installed from npm.

Enable no-webpack-loader-syntax rule in eslint-config-react-app.

This reverts commit 1ef6ea5.

 - babel-preset-react-app@1.0.0
 - create-react-app@0.6.0
 - eslint-config-react-app@0.3.0
 - react-dev-utils@0.3.0
 - react-scripts@0.7.0